Hysteresis methods for an always-on mobile station

ABSTRACT

A system and method of packet zone hysteresis for a mobile station is presented. When a short data burst is to be sent on the control channel, a check is made to see if packet zone hysteresis might have caused the PCF-PSDN interface to be torn down, and if necessary, this interface is re-established by performing a packet data service reconnect to thereby enable transmission of the short data burst.

RELATED APPLICATION

This application is a continuation-in-part of U.S. application Ser. No.11/075,956 filed Mar. 9, 2005.

FIELD OF THE APPLICATION

The application relates to wireless systems and more particularly topacket data reconnect in wireless systems.

BACKGROUND

To comply with the 3GPP2 CDMA packet data services standard “3GPP2C.S0017-012-A v1.0: Packet data Service Options for Spread SpectrumSystems: Service Options 33 and 66” (also known as TIA-707.12-B), amobile station with a dormant packet data session is required to“reconnect” its packet data service whenever it detects a change inSystem ID (SID), Network ID (NID) or Packet Zone ID (PZID) parametersassociated with the wireless network. The reconnect process is requiredto maintain PPP (point-to-point protocol) connectivity in case thewireless network needs to move the so-called “R-P” interface (also knownas A10 and A11) between the Radio Access Network (RAN) and the Packetdata Servicing Node (PDSN) associated with the packet data service or insome cases needs to assign a new IP address to the mobile station. Thereconnect process requires the mobile station to send an originationmessage with Packet data Service option and Packet data Ready to Send(DRS) bit. The wireless network may assign a traffic channel to themobile station during the reconnect process.

A feature called “packet zone hysteresis” is included in 3GPP2C.S0017-012-A v1.0 in order to minimize the number of packet datareconnects when the mobile station moves back and forth between twosystems while in a dormant state (such as SID/NID/PZID boundary). Toimplement the hysteresis feature, a mobile station keeps track ofvisited systems in a list which is called “Packet Zone List” in 3GPP2C.S0017-012-A-each entry except the most recently added entry has ahysteresis timer. If a mobile station revisits a system whose hysteresistimer has not expired yet and it does not have any packet data to send,then it refrains from reconnecting its packet data service until thehysteresis timer has expired.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments will now be described with reference to theattached drawings in which:

FIG. 1 is a block diagram of an example wireless system featuring amobile station having hysteresis activation methods;

FIG. 2 is a table of an example packet zone list;

FIGS. 3 and 4 are flowcharts of conventional methods of hysteresisactivation in the mobile station of FIG. 1;

FIG. 5 is a block diagram of an example wireless system featuring amobile station having hysteresis reset methods in accordance with anembodiment of the application;

FIGS. 6 through 11B are flowcharts of methods of hysteresis reset inaccordance with an embodiment of the application;

FIG. 12 is a flowchart of another method of hysteresis reset inaccordance with an embodiment of the application;

FIG. 13 is an example timeline of a mobile station performing packetdata reconnects according to conventional methods;

FIG. 14 is an example timeline of a mobile station performing packetdata reconnects according to an embodiment of the application;

FIG. 15 is a block diagram of an example wireless system featuring amobile station having a hysteresis activation method in accordance withan embodiment of the application;

FIG. 16 is a flowchart of a method of hysteresis activation inaccordance with an embodiment of the application; and

FIG. 17 is a flowchart of another method of hysteresis activation inaccordance with an embodiment of the application.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A broad aspect provides a method in a mobile station comprising:performing packet zone hysteresis to reduce a number of packet dataservice reconnects when a mobile station ping-pongs between multiplepacket zones; when a short data burst needs to be transmitted on acontrol channel, performing a packet data reconnect if necessary tosupport transmitting the short data burst.

Hysteresis Activation

Referring to FIG. 1, a block diagram of an example wireless systemfeaturing a mobile station having hysteresis activation methods isshown. The wireless system has a plurality of PDSNs (packet data servicenodes) 14, 20 coupled together through an IP network 16. A first PDSN 14is coupled to a plurality of BSCs/PCFs (base station controllers/packetcontrol functions) 10, 12. The PCF is typically collocated with a BSC orresident with BSC functionality. The first PDSN 14 is coupled to theBSC/PCF 10 through an R-P interface 28. Each BSC supports a respectivewireless network having details that are not shown with exception of asingle BTS (base station transceiver) 30 shown under the control of BSC10. The single BTS 30 is coupled to a mobile station 32 through awireless connection 34. Coverage areas are SID/NID/PZID zones havingassociated with them a SID (system ID), a NID (network ID), and a PZID(packet zone ID). The BSC 10 has a coverage area 22 having a networkidentifier NID₁, and a registration zone ID REGZONE₁ while the BSC 12has a coverage area 24 having a network identifier NID₂ and aregistration zone ID REGZONE₂. A combined area 26 through which packetservice is provided by the PDSN 14 has a packet zone ID PZID₁ and asystem ID SID₁. A second PDSN 20 is coupled to a single BSC/PCF 18. Thesingle BSC/PCF 18 has a coverage area 27 having a NID₃, SID₃, and PZID₃.

In operation, the mobile station 32 is required by the CDMA packet dataservice option standard, 3GPP2 C.S0017.12-A v1.0, to perform a packetdata reconnect in certain cases when it detects a change inSID/NID/PZID. The packet data reconnect allows the wireless system totrack the mobile station 32 so that packet data may be delivered to themobile station 32. In some cases when the mobile station 32 is on aboundary between different SID/NID/PZID zones, an excessive number ofpacket data reconnects can occur. In order to minimize the number ofpacket data reconnects, the mobile station 32 is equipped with areconnect hysteresis feature.

According to the reconnect hysteresis feature defined in 3GPP2C.S0017-012-A v1.0, if the mobile station 32 has recently performed apacket data reconnect to a SID/NID/PZID zone, then it will not performanother packet data reconnect to the SID/NID/PZID zone when the mobilestation 32 revisits within a certain time period since its last visit.For example, if the mobile station 32 has recently visited the coveragearea 24 and moves from the coverage area 22 to the coverage area 24,then it will detect a change in the NID from NID₁ to NID₂ but will notperform a packet data reconnect until a certain time period has expiredsince the mobile station 32 last visited the coverage area 24. In orderto keep track of recently visited SID/NID/PZID zones, the mobile station32 preferably maintains a packet zone list, which contains a list ofrecently visited SID/NID/PZID zones.

Turning now to FIG. 2, a table of an example packet zone list is shown,as indicated at 50. The packet zone list contains an identification ofSID/NID/PZID zones recently visited by the mobile station 32 andrespective hysteresis timers T₁, . . . T_(N). The packet zone list has amaximum length, which specifies how many entries can be entered. Theentries are ordered with newer entries on top and older entries onbottom. The newest entry in the packet zone list (i.e. topmost entry)does not have an active hysteresis timer. Before a new entry is added tothe packet zone list, a hysteresis timer is activated for the newestentry currently in the list and then the new entry is added without anactive hysteresis timer. The reconnect hysteresis feature is used sothat the mobile station 32 does not immediately perform a packet datareconnect after changing packet zones to a zone that was previouslyvisited within some time interval.

Turning now to FIGS. 3 and 4, flowcharts of conventional methods ofhysteresis activation in the mobile station 32 are shown. FIG. 3 showsbehavior of the mobile station 32 when it sends or receives packet data.If the mobile station 32 has sent or received user packet data at step100, then at step 105 the mobile station 32 deletes all entries in thepacket zone list except for the newest entry. At step 110, the mobilestation 32 starts a packet zone hysteresis activation timer. If thepacket data exchange was on a traffic channel, then the packet zonehysteresis activation timer starts when the mobile station 32 goesdormant. For the case of a short packet data burst on the commonchannel, the mobile station 32 will already be dormant. At step 115, themobile station sets the maximum length of the packet zone List to 1.This effectively disables the reconnect hysteresis feature since thepacket zone list cannot maintain a record of previously visitedSID/NID/PZID zones. When the packet zone hysteresis activation timerexpires, hysteresis will be re-activated. While hysteresis iseffectively disabled, any change in the SID/NID/PZID parameters triggersa packet data reconnect. FIG. 4 shows behavior of the mobile station 32when the packet zone hysteresis activation timer expires. Once thepacket zone hysteresis activation timer expires at step 200, then atstep 205 the maximum length of the packet zone list is set back to beinggreater than one so that the packet zone list enables multiple entries.At this point, the mobile station 32 has activated hysteresis but haslost entries in the packet zone list.

Hysteresis is disabled whenever the mobile station 32 sends or receivespacket data and is not re-activated for a period of time after sendingor receiving packet data. Furthermore, when hysteresis is re-activated,the packet zone list is cleared except for the most recent entry. Thisis the case even for a very quick packet data exchange such as receptionof a single email message, sending a calendar/contact update, or sendinga keep alive ping. Therefore, sending or receiving packet data impairsthe reconnect hysteresis feature. As a result, excessive packet datareconnects may occur for example when the mobile station 32 alternatesbetween two SID/NID/PZID zones, which may occur near zone barriers oroverlaps. This may reduce battery life of the mobile station 32 andconsume cellular air-interface capacity.

Turning now to FIG. 13, an example timeline of a mobile stationperforming packet data reconnects according to conventional methods isshown. This example timeline provides a demonstration of how a mobilestation such as the mobile station 32 shown in FIG. 1 performs packetdata reconnects. In this example, there are at least three basestations: A, B, and C. As described earlier with reference to FIG. 1,each base station has a respective coverage area or SID/NID/PZID zone.Across the top of FIG. 13, provided is a sequence of base stationshaving respective SID/NID/PZID zones to which the mobile station detectsto be strongest. The mobile station detects a different SID/NID/PZIDzone to be strongest every 10 seconds. This scenario may occur forexample when mobile station resides on a SID/NID/PZID boundary betweenthree SID/NID/PZID zones. Packet data reconnects and packet dataexchanges occur and are provided across the middle. Across the bottom,contents of the packet zone hysteresis list are shown.

Initially, the packet zone hysteresis list is empty except for thecurrent zone, which is initially A. At the beginning, the mobile stationdetects A, then B, and then C to be strongest. As these transitionsoccur before any respective hysteresis timers expired, the packet zonehysteresis list contains an identification of all three SID/NID/PZIDzones and respective hysteresis timers for A and B after the secondpacket data reconnect (abbreviated as PD reconnect). A packet dataexchange occurs shortly after, which clears A and B from the packet zonehysteresis list. Hysteresis is disabled for duration of the packet zonehysteresis activation timer, which is 30 seconds in this example. Duringthis time, packet data reconnects occur whenever the mobile stationdetects a different SID/NID/PZID zone to be strongest. After the packetzone hysteresis activation timer expires, hysteresis list isre-activated and entries in the packet zone hysteresis list can beentered. However, packet data reconnects continue to occur every 10seconds until the mobile station has A, B, and C in the packet zonehysteresis list with respective active timers for A and C.

Hysteresis Reset

Turning now to FIG. 5, a block diagram of an example wireless systemfeaturing a mobile station having hysteresis reset methods in accordancewith an embodiment of the application is shown. With the embodiment ofFIG. 5, the wireless system is the same as that shown in FIG. 1 andtherefore the description will not be repeated. However, FIG. 5 shows amobile station 33 equipped with a hysteresis reset function 35. Thebehaviour of the hysteresis reset function 35 will be described indetail below with various examples. The hysteresis reset function 35 canbe implemented as part of software residing on the mobile station 33; itcan be implemented in hardware or firmware; alternatively it can beimplemented as an appropriate combination of software, hardware andfirmware. Also, while the hysteresis reset function 35 is shown as adiscrete functional element, it is to be understood that it can also beimplemented by making a series of modifications to software that isotherwise compliant with existing standards. For example, existingmobile stations have the capability to comply with 3GPP2 C.S0005 for theair-interface and 3GPP2 C.S0017-012-A for packet data services. Thehysteresis reset function 35 can be embodied through a series of one ormore changes to the otherwise standard compliant functionality.

It is to be very clearly understood that the wireless system depicted inFIG. 5 is for the purpose of example and explanation only. An arbitraryarrangement of components is contemplated. Furthermore, the BSC/PCF, BTShierarchy within a given network is but one example of a method ofproviding an air-interface through to a mobile station. Otherhierarchies may alternatively be implemented.

Turning now to FIGS. 6 through 11B, flowcharts of methods of hysteresisreset are shown. One or more, preferably all, of these methods may beimplemented in a mobile station, for example, by the hysteresis resetfunction 35 of the mobile station 33 shown in FIG. 5. During an activepacket data exchange there may be time intervals during which no packetdata is being sent or received. A packet zone hysteresis reset timer isintroduced, which gives a maximum time duration for which any activepacket data exchanges collectively can go without sending or receivingpacket data during which the packet zone hysteresis list is maintainedand after which is to be cleared.

Behavior is introduced for common channel transmissions and trafficchannel transmissions. While preferably the behavior for both types oftransmission is implemented, in some instances, one or the other may beimplemented. According to 3GPP2 C.S0005-D v1.0 and 3GPP2 C.S0017.12-Av1.0, the mobile station and infrastructure may exchange small packetson the common channel rather than setting up a traffic channel bysending “Short Packet data Bursts” on the common channel.

FIG. 6 shows the behavior of a mobile station when it sends or receivespacket data using a short packet data burst on the common channel. Ifthe mobile station sends or receives packet data using a short packetdata burst at step 300, then it starts the packet zone hysteresis resettimer at step 305. Rather than deleting entries in the packet zone listother than the current entry, entries in the packet zone list withrespective hysteresis timers T₁, . . . T_(N) are maintained. In thismanner, hysteresis can be continued after a packet data exchange iscomplete using the existing entries. It is to be noted that there aremany logically equivalent ways of achieving this functionality withoutnecessarily implementing a list, or implementing timers.

FIG. 7 shows the behavior of the mobile station when the mobile stationsends or receives packet data on a traffic channel. If the mobilestation sends or receives packet data on a traffic channel at step 350,then it goes dormant at step 355. In some embodiments, the trafficchannel does not immediately go dormant, but rather stays active forsome period to allow further traffic to be sent or received. Thesending/receiving of traffic at 350 can be considered to include anysuch traffic that is sent/received before the traffic channel goesdormant. When the mobile station becomes dormant, a traffic channel isno longer maintained. If the mobile station determines that packet dataexchange is complete at step 360, then the mobile station takes nofurther action. If the packet data exchange is determined to beincomplete, then the mobile station starts the packet zone hysteresisreset timer at step 365. In both cases, entries in the packet zone listwith respective hysteresis timers T₁, . . . T_(N) are maintained.

There are many ways in which the mobile station can determine whether ornot packet data exchange is complete. For example, if the mobile stationsends an application layer packet (such as a email message, a portion ofan email message, a calendar update, an address book update, a “ping”,or a message containing a combination of these) and it receives anapplication layer acknowledgement and expects no further packet datafrom the application server (this could be understood based onapplication behavior, it could be signaled explicitly via packet datasent by the application server, or it could be based on a timeout withno further packet data received from the application server), then itmay determine that packet data exchange is complete. Another way themobile station may determine that packet data exchange is complete is ifa particular application is closed or deactivated by the user. Oneexample would be a web browser. If the user closes a web browser and noother applications are involved in a packet data exchange, the mobilemay determine that the packet data exchange is complete. When there aremultiple applications on the mobile device, the mobile will determinethat the packet data exchange is complete only when all applicationsconsider their packet data exchanges complete and no packet data fromthe wireless network is expected. It is to be understood that there arenumerous ways in which the mobile station can determine whether or notpacket data exchange is complete and the application is not limited tospecific examples provided herein.

Prior to expiry of the packet zone hysteresis reset timer, the packetzone hysteresis list is maintained notwithstanding sending and/orreceiving packet data as a short packet data burst (described withreference to FIG. 6) and/or on a traffic channel (described withreference to FIG. 7). Entries in the packet zone list are not clearedand the maximum size of the packet zone list is not changed.Furthermore, the mobile station continues to keep track of when thepacket data reconnects occur by adding entries to the packet zone listand setting the respective hysteresis timers T₁, . . . T_(N) wheneverthe mobile station performs packet data reconnects.

Turning now to FIG. 8, the behavior of the mobile station when thehysteresis reset timer expires is shown. If the mobile station detectsthat the hysteresis reset timer has expired at step 500, then itdetermines whether or not packet data exchange is complete at step 505.If the mobile station determines that packet data exchange is complete,then the mobile station does nothing. Therefore, if there are entries inthe packet zone list having respective hysteresis timers T₁, . . .T_(N), then these entries are preserved. Alternatively, if the mobilestation determines that packet data exchange is not complete, then atstep 510 the mobile station clears all but the most recent entry in thepacket zone list. Therefore, if the mobile station detects a change inSID/NID/PZID while dormant, then it will immediately perform a packetdata reconnect and be able to complete packet data exchange in a newSID/NID/PZID zone. At this point, the packet zone list is built up againas new zones are entered.

The description of FIG. 8 and other Figures refers to entries being“cleared” from the packet zone list. In the context of this description,such clearing is intended to mean that a packet zone whose entry hasbeen “cleared” is not subject to packet zone hysteresis any more. Thisdoes not necessitate physical removal of the entry, although that is oneoption. In another example, a mobile station may leave entries in thepacket zone list and instead advance respective hysteresis timers T₁, .. . T_(N) so as to allow packet data reconnects to occur without unduedelay. In yet another example, the mobile station may leave entries inthe packet zone list and instead mark them as inactive for the purposeof hysteresis.

FIG. 9 shows a method of canceling the packet zone hysteresis resettimer upon detecting that packet data exchange is complete. If themobile station detects that that packet data exchange is complete atstep 400, then it cancels the packet zone hysteresis reset timer if itis active at step 405. By canceling the packet zone hysteresis resettimer when packet data exchange is complete, the packet zone hysteresislist is not reset. Instead, entries in the packet zone list withrespective hysteresis timers T₁, . . . T_(N) are maintained.

In some embodiments, when implementing the method of FIG. 9, theyes-path of step 505 in FIG. 8 is never executed because the method ofFIG. 9 ensures that the packet zone hysteresis reset timer is cancelledif packet data exchange is complete. In other embodiments, it ispossible for the yes-path of step 505 in FIG. 8 to be executed forexample if packet data exchange completes at the same time as the packetzone hysteresis reset timer expires. In this example, the method of FIG.9 will execute, but the packet zone hysteresis reset timer is notcancelled as it has expired. Since the packet zone hysteresis resettimer has expired and packet data exchange is complete, step 500 and theyes-path of step 505 in FIG. 8 are executed.

Turning now to FIG. 10, the behaviour of the mobile station when itmoves to a different SID/NID/PZID zone is shown. If the mobile stationmoves to a different SID/NID/PZID zone at step 600, then it determineswhether or not the hysteresis reset timer is active at step 605. If thehysteresis reset timer is not active, then at step 607 the mobilestation will add the different SID/NID/PZID as the most recent entry inthe packet zone list if there is not already an entry and will start therespective hysteresis timer for the previous SID/NID/PZID, and willperform a reconnect if the different zone was not on the list. An activepacket zone hysteresis reset timer (yes path step 605) means that thereis an incomplete packet data exchange because if packet data exchangewas determined to be complete, then at step 400 in FIG. 9 the packetzone hysteresis reset timer would be cancelled. If packet data exchangeis determined to be incomplete and the mobile station has determinedthat it is in a different SID/NID/PZID zone, then the mobile stationwill perform a packet data reconnect in order to maintain packet dataconnectivity. The mobile station clears the current SID/NID/PZID zonefrom the packet zone list if it is in the packet zone list at step 610and perform a packet data reconnect for the current SID/NID/PZID at step615. Clearing the current SID/NID/PZID from the packet zone list mayinclude cancelling the respective hysteresis timer for the SID/NID/PZID.While the hysteresis reset timer is active and there is an incompletepacket data exchange, the mobile station will always be connected to thecurrent SID/NID/PZID zone, but will still maintain hysteresisinformation for previously visited SID/NID/PZIDs.

Turning now to FIG. 11A, shown is the behaviour of the mobile stationwhen it needs to send a short packet data burst to which a response isexpected and the mobile station may not have performed a reconnect inthe current zone and as such the system may not know where the mobilestation is. If the mobile station needs to send a short packet databurst to which a response is expected at step 700, then at step 705 themobile station determines whether or not it has moved to a differentpacket data zone. The mobile station knows if it has moved to adifferent packet data zone when the most recent entry in the packet zonelist is different than the current packet zone. If the mobile stationdetermines that it has moved to a different packet data zone, then atstep 710 the mobile station clears the SID/NID/PZID zone from the packetzone list and performs a packet data reconnect at step 715 to let thesystem know where it is. Steps 705, 710, and 715 ensure that the mobilestation is connected to the current SID/NID/PZID zone. At step 720, themobile station sends the short packet data burst. This embodimentassumes that the mobile station need not necessarily perform a reconnectto send a short packet data burst. However, if a response is expected,it will need to do a reconnect.

In some embodiments, packet data is sent as a short packet data burst onthe common channel as described with reference to FIG. 6. In otherembodiments, the packet data is sent on a traffic channel as describedwith reference to FIG. 7. In some embodiments, at step 715 the mobilestation specifies whether the common channel or a traffic channel is tobe used for sending the packet data. In particular, during the packetdata reconnect, the mobile station specifies in the origination messagethe DRS (packet data ready to send) bit. By setting DRS=1, the mobilestation requests a traffic channel. By setting DRS=0, a traffic channelis not requested.

The method of FIG. 11A allows the mobile station to send a short packetdata burst and receive a response while maintaining the hysteresis list.If the mobile station has moved to a different packet zone and needs tosend a short packet data burst to which a response is expected, then itperforms a packet data reconnect in order to inform the network of itslocation. Preferably, the packet data reconnect is performed prior tosending packet data as it can request a traffic channel for the packetdata exchange. In other embodiments, the packet data reconnect isperformed immediately after sending packet data. Note that if the mobilewere not expecting a response it could avoid steps 705, 710, and 715.

The methods of FIGS. 10 and 11A are similar in that they are concernedwith performing a packet data reconnect upon detecting that the mobilestation has moved to a new packet data zone and a packet data exchangeis active (described with reference to FIG. 10) or known to becomeactive (described with reference to FIG. 11A). Once packet data exchangebecomes active at step 720, then as described earlier with reference toFIGS. 6, 7 and 9, the packet zone hysteresis reset timer is started uponpacket data exchange that is determined to be incomplete. As describedearlier with reference to FIG. 8, if packet data exchange is determinedto be incomplete when the packet zone hysteresis reset timer expires,then all entries except for the most recent entry in the packet zonelist are cleared so that a packet data reconnect can be performed andpacket data exchange can be completed. However, as described earlierwith reference to FIGS. 8 and 9, if packet data exchange is completedbefore the packet zone hysteresis timer expires, then the entries in thepacket zone list are not cleared.

As discussed in detail above, TIA-707.12-B includes a packet zonehysteresis that reduces the number of packet data reconnects when amobile station ping-pongs between multiple packet zones. Because of thisfeature, the mobile station does not need to perform a packet datareconnect when moving to a packet zone in its hysteresis list.TIA-707.12-B also includes a feature called “Short Data Burst” whichallows the mobile station to send short data packets on the controlchannel rather than setting up a traffic channel. Disadvantageously,TIA-707.12-B does nothing to support interaction between the packet zonehysteresis feature and the short data burst feature. The so-called“A-10” connection, also referred to as the R-P interface and moregenerally the PCT-PDSN interface, is involved in this control channel.After a mobile station moves into the coverage area of a different PCF,a packet data reconnect is needed to cause the A10 connection from thePDSN to be moved to the new PCF, and to thereby enable the short databurst feature to continue to function. According to the standard ascurrently defined, if the mobile station sends a short data burst whenin a zone not most recent in its hysteresis list, the data will be lostbecause the A10 is not moved. While the expression “short data burst” isintroduced above in the context of a particular standard, moregenerally, this is intended to mean any short data burst on a controlchannel as opposed to a traffic channel.

Turning now to FIG. 11B, shown is the behaviour of a mobile stationprovided by another embodiment when it needs to send a short packet databurst but may not have performed a reconnect in the current zone. If themobile station needs to send a short packet data burst at step 725, thenat step 705 the mobile station determines whether or not it has moved toa different packet data zone. The mobile station knows if it has movedto a different packet data zone when the most recent entry in the packetzone list is different than the current packet zone. If the mobilestation determines that it has moved to a different packet data zone,then at step 710 the mobile station clears the SID/NID/PZID zone fromthe packet zone list and performs a packet data reconnect at step 715.At step 720, the mobile station sends the short packet data burst. Thisembodiment assumes the mobile station needs to have performed areconnect to send a short packet data burst.

In some implementations, the short data burst and the reconnect areperformed at the same time by encapsulating the short data burst withinanother message used for the reconnect. In a very particular example ofthis, the mobile station checks the C.S0005 protocol revision of thebase station. C.S0005 specifies the signaling protocol for the airinterface. The protocol revision is broadcast from the base station toall mobile stations on a control channel (an 8-bit field called P_REV)to tell the mobile station its protocol revision. A C.S0005-D basestation sets the field to ‘00001011’. If the protocol revision of thebase station is C.S0005-D or later the mobile station performs the shortdata burst and the reconnect at the same time by encapsulating the shortdata burst in the C.S0005-D Reconnect Message. If the protocol revisionof the base station is less than C.S0005-D, the mobile station sends anOrigination Message and the Data Burst Message as separate messages.

A specific solution to the short data burst problem has been detailedabove. More generally, a mobile station can deal with this by performingpacket zone hysteresis to reduce a number of packet data servicereconnects when a mobile station ping-pongs between multiple packetzones, where packet zone hysteresis is to be interpreted very generallyin this context, and in advance of sending a short data burst on acontrol channel, performing a packet data reconnect if necessary tosupport transmitting the short data burst.

Many of the detailed examples presented assume that packet data servicereconnect occurs across changes in SID/NID/PZID. More generally,reconnect is considered to occur across changes in packet data servicereconnect zone. The reconnect zone does not have to be an actualparameter. In the particular examples given, any time any one ofSID/NID/PZID changes, the reconnect zone changes. Other reconnecttriggers are contemplated.

Turning now to FIG. 12, a flowchart of another method of hysteresisreset in accordance with an embodiment of the application is shown. Thismethod may be implemented in a mobile station, for example, by thehysteresis reset function 35 of the mobile station 33 shown in FIG. 5.At step 1201, the mobile station maintains an identification ofpreviously visited packet data service reconnect zones notwithstandingreceipt or transmission of packet data. At step 1202, the mobile stationperforms packet data service reconnects using reconnect zone hysteresisusing the identification of previously visited packet data servicereconnect zones.

The mobile station performs packet data service reconnects usingreconnect zone hysteresis. According to reconnect zone hysteresis, themobile station waits until a certain time has passed since last visitinga visited packet data service reconnect zone before performing a packetdata service reconnect in the visited packet data service reconnectzone. There are many ways to implement such reconnect zone hysteresis.In one example, the mobile station maintains hysteresis information,namely an identification of visited packet data service reconnect zonesand a respective time identification since the mobile station lastvisited each of the visited packet data service reconnect zones. In thisexample, when the mobile station moves to a packet data servicereconnect zone, it will know if the packet data service reconnect zonehas been recently visited based on its identification of visited packetdata service reconnect zones. If the mobile recognises that the packetdata service reconnect zone has been recently visited, then it mayrefrain from performing a packet data service reconnect until therespective time identification indicates that enough time has passedsince visiting the packet data service reconnect zone.

In the described examples, an entry is made into the hysteresis list fora new zone (i.e. not previously visited) although a reconnect isperformed in the new zone, and no timer is started. On this basis, ifthe most recent entry is for the current zone, then the mobile stationknows that a reconnect has been performed for the current zone. Settingthe maximum length of the list to one means that a reconnect will happenevery time the zone changes and hysteresis has effectively beende-activated. There are many equivalent ways of achieving this. Forexample, entries might be made only when exiting a visited zone, withsome other indication maintained of whether a reconnect has beenperformed or not for the current zone. In that case, setting the maximumlength of the list to zero would result in a reconnect every time thezone changes. Furthermore, more generally this effect can be achievedwithout necessarily doing anything with the maximum length of the list,but rather by simply activating or de-activating hysteresis in anysuitable fashion.

Turning now to FIG. 14, an example timeline of a mobile stationperforming packet data reconnects according to an embodiment of theapplication is shown. This example timeline provides a demonstration ofhow a mobile station performs packet data reconnects when it isimplemented with one or more, preferably all, of the methods describedwith reference to FIGS. 6 through 12. Across the top of FIG. 14,provided is a sequence of base stations having respective SID/NID/PZIDzones to which the mobile station detects to be strongest. This sequenceis the same as the sequence described with reference to FIG. 13. Also,FIG. 14 shows a packet data exchange, which occurs at the same time asthe packet data exchange in FIG. 13. However, significantly fewer packetdata reconnects are shown in FIG. 14.

Initially, the packet zone hysteresis list is empty except for thecurrent zone, which is initially A. At the beginning, the mobile stationdetects A, then B, and then C to be strongest. As these transitionsoccur before any respective hysteresis timers expired, the packet zonehysteresis list contains an identification of all three SID/NID/PZIDzones and respective hysteresis timers for A and B after the secondpacket data reconnect (abbreviated as PD reconnect). A packet dataexchange commences shortly after and is completed before the trafficchannel goes dormant. This corresponds to the yes path of step 360 ofFIG. 7. The mobile station sends packet data, receives the response,determines that the packet data exchange is complete, goes dormant, anddoes not start the hysteresis reset timer. The packet zone hysteresislist is not cleared at any point on the timeline. The mobile stationdoes not perform packet data reconnects for the remainder of thetimeline as the mobile station has maintained the packet zone hysteresislist.

Hysteresis Activation Embodiment

Turning now to FIG. 15, a block diagram of an example wireless systemfeaturing a mobile station having a hysteresis activation method inaccordance with an embodiment of the application is shown. With theembodiment of FIG. 15, the wireless system is the same as that shown inFIG. 1 and therefore the description will not be repeated. However, FIG.15 shows a mobile station 36 equipped with a hysteresis activationfunction 37. The behaviour of the hysteresis activation function 37 willbe described in detail below with various examples. The hysteresisactivation function 37 can be implemented as part of software residingon the mobile station 33; it can be implemented in hardware or firmware;alternatively it can be implemented as an appropriate combination ofsoftware, hardware and firmware. Also, while the hysteresis activationfunction 37 is shown as a discrete functional element, it is to beunderstood that it can also be implemented by making a series ofmodifications to software that is otherwise compliant with existingstandards. For example, existing mobile stations have the capability tocomply with 3GPP2 C.S0005 for the air-interface and 3GPP2 C.S0017-012-Afor packet data services. The hysteresis activation function 37 can beembodied through a series of one or more changes to the otherwisestandard compliant functionality.

It is to be very clearly understood that the wireless system depicted inFIG. 15 is for the purpose of example and explanation only. An arbitraryarrangement of components is contemplated. Furthermore, the BSC/PCF, BTShierarchy within a given network is but one example of a method ofproviding an air-interface through to a mobile station. Otherhierarchies may alternatively be implemented.

Turning now to FIG. 16, a flowchart of a method of hysteresis activationin accordance with an embodiment of the application is shown. Thismethod allows hysteresis to be re-activated upon detecting that packetdata exchange is complete. This method may be implemented in a mobilestation, for example, the hysteresis activation function 37 of themobile station 36 shown in FIG. 15.

If the mobile station has sent or received user packet data at step1501, then at step 1502 the mobile station deletes all entries in thepacket zone list except for the newest entry. At step 1503, the mobilestation starts a packet zone hysteresis activation timer. If the packetdata exchange was on a traffic channel, then the packet zone hysteresisactivation timer starts when the mobile station goes dormant. For thecase of a short packet data burst on the common channel, the mobilestation will already be dormant. At step 1504, the mobile station setsthe maximum length of the packet zone list to 1. This effectivelydisables the reconnect hysteresis feature since the packet zone listcannot maintain a record of previously visited SID/NID/PZID zones. Whenthe packet zone hysteresis activation timer expires at step 1505 or thepacket data exchange is determined to be complete at step 1506,hysteresis is re-activated at step 1507 by setting the maximum length ofpacket zone list back to multiple entries. Advantageously, if packetdata exchange completes before the packet zone hysteresis activationtimer expires, then hysteresis is re-activated without waiting for thepacket zone hysteresis activation timer to expire. In some embodiments,the packet zone hysteresis activation timer is cancelled at step 1507 ifit is still active.

Turning now to FIG. 17, a flowchart of another method of hysteresisactivation in accordance with an embodiment of the application is shown.This method may be implemented in a mobile station, for example, thehysteresis activation function 37 of the mobile station 36 shown in FIG.15. At step 1701, while reconnect zone hysteresis is active, the mobilestation maintains an identification of previously visited packet dataservice reconnect zones and performs packet data service reconnectsusing reconnect zone hysteresis using the identification of previouslyvisited packet data service zone. At step 1702, upon commencing a packetdata exchange, the mobile station de-activates reconnect zonehysteresis. At step 1703, immediately upon determining that packet dataexchange is complete, the mobile station re-activates reconnect zonehysteresis. De-activating and re-activating reconnect zone hysteresismight for example be achieved by setting the maximum size of ahysteresis list. Other mechanisms can be used.

Mobile Stations Unaware of Packet Data Exchanges Completing

Many of the methods shown in FIGS. 6 through 12 and 16 through 17involve the mobile station determining whether or not a packet dataexchange is complete. Several examples have been provided as to how amobile station can determine that a packet data exchange is complete.However, some mobile stations are unaware of whether or not packet dataexchanges are complete as they operate at a lower layer than for examplean application causing the packet data exchange. Therefore, these mobilestations are not able to determine that any packet data exchange iscomplete. Accordingly, in some embodiments these mobile stations assumethat packet data exchange is incomplete when executing method stepsrequiring that the mobile station determine whether or not packet dataexchange is complete.

In some embodiments, one or more of the methods shown in FIGS. 6 through12 are simplified when implemented in a mobile station by removingprocessing paths following determination of a packet data exchange beingcomplete. For example, with reference to FIG. 8, upon expiry of thehysteresis reset timer, the mobile station deletes all but the mostrecent entry in the packet zone list. Therefore, a packet data exchangetriggers all but the most recent entry in the packet zone to be deletedat a time period after the packet data exchange commences. During thistime, the mobile station is still able to perform packet data reconnectsto packet data zones that are included in the packet zone list.

Another embodiment provides a computer readable medium havinginstructions stored thereon for execution by a mobile station toimplement any of the methods described herein.

Numerous modifications and variations of the present application arepossible in light of the above teachings. It is therefore to beunderstood that within the scope of the appended claims, the applicationmay be practised otherwise than as specifically described herein.

1. A method in a mobile station comprising: performing packet zonehysteresis to reduce a number of packet data service reconnects when amobile station ping-pongs between multiple packet zones; when a shortdata burst needs to be transmitted on a control channel, performing apacket data reconnect if necessary to support transmitting the shortdata burst.
 2. The method of claim 1 wherein performing a packet datareconnect if necessary comprises: if a current packet zone is not a mostrecently visited packet zone, performing a packet data reconnect.
 3. Themethod of claim 1 wherein performing packet zone hysteresis comprises:upon visiting a packet zone that has not been previously visited withina specified time, performing a packet data reconnect; upon visiting apacket data service that has been previously visited within a specifiedtime, not performing a packet data reconnect.
 4. The method of claim 1wherein performing a packet data reconnect if necessary comprises: if acurrent packet zone is not a most recently visited packet zone, andperforming a packet data reconnect.
 5. The method of claim 1 whereinperforming packet zone hysteresis comprises: maintaining anidentification of previously visited packet data service reconnect zonesnotwithstanding receipt or transmission of packet data; and performingpacket data service reconnects using reconnect zone hysteresis using theidentification of previously visited packet data service reconnectzones.
 6. The method of claim 1 further comprising: transmitting theshort data burst and a message for reconnect in a single message.
 7. Themethod of claim 6 wherein the single message is a reconnect message. 8.The method of claim 1 further comprising: determining if a base stationto which a reconnect is to be performed supports sending the short databurst encapsulated within a reconnect message; if the base stationsupports sending the short data burst encapsulated within a reconnectmessage, sending the short data burst encapsulated within a reconnectmessage, and otherwise sending a message for packet data servicereconnect separately from the short data burst.
 9. The method of claim 8wherein determining if a base station to which a reconnect is to beperformed supports sending the short data burst encapsulated within areconnect message comprises: examining a C.S0005 revision of the basestation.
 10. The method of claim 8 determining if a base station towhich a reconnect is to be performed supports sending the short databurst encapsulated within a reconnect message comprises: examining aC.S0005 revision of the base station; if the C.S0005 indicates revisionD or higher, determining that the short data burst can be sentencapsulated within a reconnect message.
 11. A mobile station adapted toimplement the method of claim
 1. 12. A mobile station adapted toimplement the method of claim
 2. 13. A mobile station adapted toimplement the method of claim
 3. 14. A mobile station adapted toimplement the method of claim
 4. 15. A mobile station adapted toimplement the method of claim
 5. 16. A mobile station adapted toimplement the method of claim
 6. 17. A mobile station adapted toimplement the method of claim
 7. 18. A mobile station adapted toimplement the method of claim
 8. 19. A mobile station adapted toimplement the method of claim
 9. 20. A mobile station comprising ahysteresis activation function adapted to implement the method of claim1.